Release 10.1A: OpenEdge Development:
Progress Dynamics Web Development Guide

Progress Dynamics and WebSpeed

Progress Dynamics Web applications use the basic WebSpeed architecture. In Figure 2–1, the WebSpeed components that are different in Progress Dynamics are shown in bold.

The Progress WebSpeed® Messenger and NameServer are the same as those used in a standard WebSpeed configuration. In fact, as Figure 2–1 implies, a standard WebSpeed configuration can coexist with a Progress Dynamics Web configuration. Both could share the same Messenger and NameServer.

However, the Progress Dynamics Broker and Agents differ from the standard WebSpeed Broker and Agents in the following ways:

The Progress Dynamics Broker/Agent is configured with a different PROPATH setting, and with an ICFWS Session Type startup parameter. See Chapter 3, "Setting Up Progress Dynamics for Running Web Applications," for more information about configuration.
The Progress Dynamics Agent is actually composed of Dynamics managers. The Request Manager serves as the point of entry for Web requests. The User Interface Manager creates the DHTML that is sent to a client browser. The Progress Dynamics Agent depends on other Dynamics managers for various services (session management and security, for example).

For an overview of how the Progress Dynamics Agent operates, see the "How Progress Dynamics handles a Web request" section.

The Progress Dynamics Agent does not run Web objects as a standard WebSpeed Agent does. In order to build a Web application, the Progress Dynamics Agent interacts with the Repository database to build application objects.

Figure 2–1: Progress Dynamics and a WebSpeed configuration

Note: Although the Progress Dynamics Broker/Agent differs internally and functionally from the standard WebSpeed Broker/Agent, you can still manage and configure the Progress Dynamics Broker/Agent with Progress Explorer. The Progress Dynamics Brokers are listed under the WebSpeed node in the Progress Explorer tree view.